Re: [nvo3] [mpls] MPLS-RT review of draft-xu-mpls-in-udp-03

Aldrin Isaac <aldrin.isaac@gmail.com> Sun, 09 December 2012 05:51 UTC

Return-Path: <aldrin.isaac@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14ED821F8481 for <nvo3@ietfa.amsl.com>; Sat, 8 Dec 2012 21:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z9dZ-0MTmtqS for <nvo3@ietfa.amsl.com>; Sat, 8 Dec 2012 21:51:58 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id DB1DC21F846E for <nvo3@ietf.org>; Sat, 8 Dec 2012 21:51:57 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so719696bku.31 for <nvo3@ietf.org>; Sat, 08 Dec 2012 21:51:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XgfAO3hu34BgVz0Qol31LkBR3iJEQGa2ruXT7yKWzb0=; b=oEdzEfdrbCdvZYPZqq6No0C89Y5ShQ0Tc2pesl94XoHPzQKNIEOvZUSssr1Nqzyepa eYJakouBAj9QZ1lEp8FkNDOjIor9SkwFwApUWUBwmfK2PanbImOAl03xYuL8xy62wTaS iS1tJF0Tvc8vFf3uylkPgpuZnND1twTX6zGSiRghY1uU2vyhtba6Bq3s0eMVFYgNOVvl V9gFClXuYg2d0pT+zPC9oCaicrIppNd2CMN0wm4ZU+nsaKvOGKp9bI6jvofg7q2KSK4Q sH1LhJGkuVLlRf1PwoOYQdd9Hf78kXOsVX29qH9mSXy1J7Qq21KrOFMFbPxEi2Ag52nV RibQ==
MIME-Version: 1.0
Received: by 10.204.127.11 with SMTP id e11mr3335334bks.0.1355032316757; Sat, 08 Dec 2012 21:51:56 -0800 (PST)
Received: by 10.204.168.206 with HTTP; Sat, 8 Dec 2012 21:51:56 -0800 (PST)
In-Reply-To: <BB8D8AEC7DBA1F41810DCB5D38AF56AB9CC9165DAA@HQ1-EXCH02.corp.brocade.com>
References: <50A28033.3050904@pi.nu> <7347100B5761DC41A166AC17F22DF11201BCB8@eusaamb103.ericsson.se> <002a01cdcc17$5ef0dcd0$1cd29670$@olddog.co.uk> <8E15642F-5F4B-4BD3-9BE9-C4EA56AA3FDE@broadcom.com> <2691CE0099834E4A9C5044EEC662BB9D44850CB1@dfweml505-mbb.china.huawei.com> <4A6CE49E6084B141B15C0713B8993F281BD34607@SJEXCHMB12.corp.ad.broadcom.com> <2691CE0099834E4A9C5044EEC662BB9D44852ED2@dfweml505-mbb.china.huawei.com> <BB8D8AEC7DBA1F41810DCB5D38AF56AB9CC9165D88@HQ1-EXCH02.corp.brocade.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07585D24@szxeml525-mbs.china.huawei.com> <BB8D8AEC7DBA1F41810DCB5D38AF56AB9CC9165DAA@HQ1-EXCH02.corp.brocade.com>
Date: Sun, 09 Dec 2012 00:51:56 -0500
Message-ID: <CAOA2mbzcUQU-wqguABF0Rc1S2Ex1h9y4aCJazHV_ZPoKKQ66bA@mail.gmail.com>
From: Aldrin Isaac <aldrin.isaac@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary="0015175884b6e6469f04d0650bca"
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Subject: Re: [nvo3] [mpls] MPLS-RT review of draft-xu-mpls-in-udp-03
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 05:51:59 -0000

Historically there really was no MPLS enabled products that hit the right
price points and/or features needed for the DC -- but some of us operators
*have* implemented MPLS in the DC very successfully.  My observation is
that some vendors don't do MPLS/MPBGP very well and aggressively discourage
its adoption, while other vendors reserve them for their SP products for
which they  need reasons to charge a premium.  Now with support for MPLS in
merchant silicon, I don't see any good reason why MPLS-based DCVPN
solutions (IPVPN, E-VPN) should be held back, particularly if the overlay
tunnel is IP-based and MPLS labels are used for VPN context, split-horizon,
etc.


On Thursday, November 29, 2012, Melinda Shore wrote:

> On 11/29/12 5:14 PM, S. Davari wrote:
> > Regarding Technical merits, all these solutions are technically
> > sound, the issue is that we don't want to have a dozen solution to
> > the same problem.
>
> Traditionally the IETF has let the market sort out competing
> technologies rather than try to deem one "best," but there's
> got to be at least some evidence that a technology will be
> adopted.  I have to agree that MPLS in data centers is a
> tough sell.  It would be great to see some input from data
> center operators to help sort this out.
>
> Melinda
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>